WS-1945 Migrate Integration tests (Topic Page) #13595
Merged
+133
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://bbc.atlassian.net/browse/WS-1945
Migrated topic page tests to next js app as part of the migration of pages to next js. Deletes tests from src/app.
This pull request also adds and refactors integration tests for the topic pages, focusing on improving test coverage for page content and curation features. It introduces a shared test suite for verifying topic page content, applies this suite to multiple services, and updates relevant snapshot files to reflect the new and updated tests.
Test Coverage Improvements:
pageContentTests.tsto verify key aspects of topic page content, such as the first item's headline and image, the presence of curation grids, and the main HTML tag structure.pageContentTestsinto the existing cross-platform tests (crossPlatformTests.ts) and themundotopic page tests, ensuring consistent content validation across services. [1] [2]Snapshot and Test File Updates:
mundoandpidgintopic pages to capture expected headlines, images, badge images, and descriptions as part of the new and expanded tests. [1] [2]Summary
A very high-level summary of easily-reproducible changes that can be understood by non-devs, and why these changes where made.
Code changes
Developer Checklist
Testing
Ready-For-Test, Local)Ready-For-Test, Test)Ready-For-Test, Preview)Ready-For-Test, Live)Additional Testing Steps
Useful Links